Using Lists to Create Collapsible Navigation Bars

Introduction to collapsible navigation bars

Collapsible navigation bars are great ways to help guide visitors to Web pages on your site. They allow the visitor to see a limited number of items to choose from, and then click a plus sign next to the item they want to find out more information about. Collapsible navigation bars are especially helpful on Web sites with many items to navigate to because navigating a long list of items that are not grouped in any way can be frustrating for visitors.
Creating collapsible navigation bars can be complicated and time-consuming, and usually requires expertise in JavaScript. However, you can easily create great-looking collapsible navigation bars with Windows SharePoint Services and Microsoft Office FrontPage 2003.

Example

This Quick Launch navigation bar has 3 headings — Articles, Other Resources, and Sample Sites. When the page that contains this navigation bar is opened, only those headings are listed. When the visitor clicks the link next to a heading, the list of links beneath it expands, and when they click the link on expanded headings, they collapse again.
The Windows SharePoint Services list that was used to create this navigation bar contains 2 fields — Resource and Category. The Resource field contains the page links, and the Category field contains the headings in the list. The Quick Launch navigation bar is created by inserting a Web Part view of the list into the page, then grouping and sorting the list, and then converting it to an XSLT view so that formatting of the list can be perfected.

Creating the collapsible navigation list

Here are the steps we took to create the collapsible navigation list shown in the example section.

1. Create a list in Windows SharePoint Services that contains 2 fields: Resource, and Category. The Resource field should be formatted as a hyperlink, and the Category field can either be a drop-down choice or a text field.
   
   Tip: If you want to experiment with this functionality, you can download this Excel spreadsheet and then create your list from it. See the article entitled Converting an Excel Spreadsheet into a List for more information.
   
   Tip: If you want to create the list from one of the list templates, start with a Links list, then rename the Links field to Resources, then add a field called Category, and then delete the Notes field.
   
2. Open your site created with Windows SharePoint Services in Microsoft Office FrontPage 2003 and then open the page you want to insert the collapsible navigation list into.
3. Click Insert Web Part on the Data menu. The Web Parts task pane opens.
4. Click the name of the list you want to insert into your page, such as "Quick Launch List," and then click the Insert Selected Web Part button. The Web Part is inserted into your page and looks like this:
   
   
   
5. Next, right-click on the list and then select List View Properties. The Data View Details task pane opens.
6. Click the Fields link on the Data View Details task pane. The Displayed Fields dialog box opens.
7. Make sure that the only field that is displayed is the Resource field, and then click OK.
   
   
   
8. Click the Style link on the Data View Details task pane. The View Styles dialog box opens.
   
   
   
   
9. Click the Options tab on the View Styles dialog box, and then make sure that the Show toolbar with options for check box is empty. This removes the toolbar from the view.
10. Click the Sort & Group link on the Data View Details task pane. The Sort and Group dialog box opens.
11. Make sure that the only field in the Sort Order box is Category, that the Ascending radio box is selected, that the Show group header check box is selected, and that the Collapse group by default radio button is selected.
    
    
    
    The list now looks like this:
    
    
    
12. [Optional] If you do not want the headings to read "Category: " before the heading, or if you want to make other formatting changes, you can convert the data view to XSLT view and then make the edits. Right-click on the list, and then select Convert to XSLT Data View. Click and highlight "Category:" and then type Delete to remove that text. If you want to remove the "Resource" heading, click inside that text, then click Select from the Table menu, then click Row, and then click Delete Rows on the Table menu. Additionally, if you want to add some space before the Resource links, click before one of the links and then type Space until there is the right amount of space before the link. Now the list looks like this in the collapsed state:
    
    
    
    

SharePoint 2007 – Document Library Send To Feature

One of the neat new features of a SharePoint document library in SharePoint 2007 is the ability to send a document to another location. This feature is great for a couple of reasons. The first is that most teams have a collaborative area where they create content that will eventually be consumed and available for the remainder of the company. In many cases, this collaborative area is restricted to only those that belong to the team responsible for creating the content. However once the document is complete, it should be published out to a location where everyone has access. The problem with relocating the document to a less secured area is that it involves us either moving or copying it. Moving doesn’t seem like a good idea since it is likely that the team may wish to make further updates at a later time. If that is the case, then it would be most appropriate for them to make those updates in their collaborative area since that is where they do all their work. Copying involves duplicating a file and that typically introduces issues with synchronization of content. However using the Send to functionality of a document library, we can create a link from the source document to the published copy so that whenever the document is checked back in, the author will be prompted to update the published versions. Another great feature of this Send To option is the ability to create a custom location. This allows us to specify a common place that content may be published to. To do this you must go to the Advanced Settings of the document library, and specify the location of the document library you wish to publish to. Note: Make sure you specify the library url (example: http://server/sites/sitename/libraryname) and not a view of the library (example: http://server/sites/sitename/libraryname/allitems.aspx). Once you have your specified custom location, it will show up in context menu of documents in that library.

Changing Gradient Images in Sites Created with Windows SharePoint Services

Introduction to gradient images

Default Web sites created with Windows SharePoint Services contain some elements with gradient colors that you might want to replace with your own. The default home page top menu bar and the title bars for Web Parts have gradient images behind them, as do the toolbars on the tops of list and document library pages and the rich text editor toolbar on forms.

These gradient colors are determined by the Theme applied to the site. The Theme specifies a graphic to place in the background of the table cell that makes up the toolbar. For example, the top menu bar has an image that is 1 pixel wide by 28 pixels high in the background of the table cell that contains the top menu items (such as "Home", "Documents and Lists", and "Create"). The graphics are located in the http:///_layouts/images directory in your Web site.

Tip: Because files in the _layouts directory are hidden and not accessible at the file level from the Web site, if you want to use them to start with and then edit them, you should browse to them first, then right-click on them and then save them to your hard drive.
Elements to change

Gradient images are changed in Themes, so you will need to know what styles need to be changed in your custom Theme in order to change the gradient image. The table below shows the size of image needed as well as the corresponding styles to change in the custom Theme.
Element File Name Image Size
(in pixels) Example Styles to Change in Theme
Top menu bar topgrad.gif 1 x 28
.ms-bannerframe, .ms-GRheader, .ms-stormefree
Web Part title bar partgrad.gif 1 x 18
.ms-wpheader
Toolbar on list and document library pages toolgrad.gif 1 x 22
table.ms-toolbar
Rich text editor toolbar in selected state rtebnsel.gif 1 x 20

.ms-rtetoolbarsel
Rich text editor toolbar in hovered state rtetoolbarhov 1 x 20

.ms-rtetoolbarhov
How to change gradient images

Here are the steps to follow to change gradient images in your custom Theme.

1. Create the graphics files you want to use to serve as the background image to replace the gradiated images already used on your site. The files can be .jpg or .gif files.
2. Open your site created with Windows SharePoint Services in Microsoft Office FrontPage 2003.
3. Import your new graphics files into your site by clicking the Import option from the File menu, then clicking the Add Files button, and then following the prompts.
4. Click Theme from the Format menu. The Theme task pane opens.
5. Click the Theme you want to customize, and then select Customize.



6. The Customize Theme dialog box opens. Click the Text button.
7. The Customize Theme styles dialog box opens. Click the More Text Styles... button.
8. The Style dialog box opens. Click the name of the style you want to change, and then click the Modify button.
9. The Modify Style dialog box opens. Click the Format button, and then click the Border option.
10. The Borders and Shading dialog box opens. Click the Shading tab.



11. Click the Browse button on the Borders and Shading dialog box. Locate and then click on the image you want to use as the background of the table cell. Click the Open button.
12. Click the OK button 5 times.
13. Click Yes when asked if you want to save your changes. The Theme now specifies use of your custom gradient image. You can now view the changes on your Web site.

Applying a Theme to a Site Created with Windows SharePoint Services

Introduction to Themes

Themes are a powerful feature in Microsoft Office FrontPage 2003. Themes are professional coordinated collections of design elements like buttons, hover buttons, bullets, backgrounds, horizontal rules, page banners, and font and formatting choices. FrontPage 2003 includes many ready-made Themes that can be applied to Web sites created in FrontPage, Web sites created with Microsoft Windows SharePoint Services, and even documents created with Microsoft Word.
Themes are a powerful feature in Microsoft FrontPage and Web sites based on SharePoint Team Services. Themes are professional coordinated collections of design elements like buttons, hover buttons, bullets, backgrounds, horizontal rules, page banners, and font and formatting choices. FrontPage 2002 includes more than 65 pre-built Themes that can be applied to Web sites based on SharePoint Team Services, FrontPage-created sites, and even documents created with Microsoft Word. Additionally, you can take any Theme and customize the elements to give you exactly the look you want. This article discusses how to apply a Theme to a Web site based on SharePoint Team Services.

You can either change Themes on sites created with Windows SharePoint Services with your browser through the Windows SharePoint Services user interface, or you can change them using FrontPage 2003. This article outlines the steps for both methods. Note that to apply custom Themes, you must use FrontPage 2003.
Changing Themes through the browser

Changing Themes on a site created with Windows SharePoint Services is simple.

1. Browse to the home page of your Web site.
2. Click the Site Settings link at the top of the home page.



3. Click Apply theme to site in the Customization section of the Site Settings page.
4. Click the name of the Theme you want to preview.



5. Click Apply. The new Theme is applied:

Changing Themes through FrontPage 2003

Changing Themes through FrontPage 2003 is easy, and offers you more choices than applying a new Theme from a browser. Here is how to apply a new Theme to a site created with Windows SharePoint Services using FrontPage 2003.

1. Open the Web site based on Windows SharePoint Services in FrontPage 2003 (select Open Site from the File menu, then type in the URL for your site; you will need to be able to supply the user name and password for the site).

2. Select Theme from the Format menu. The Themes task pane lists all of the Themes that are available and offers a preview of each.



3. Select the Theme you want to apply by clicking on its name in the Themes list. In the example used in this article, the Spring Theme was used.

4. You can choose from the three options at the bottom of the Themes task pane:



Vivid colors - To use a bright color set, select the Vivid colors check box. To use the normal color set, clear this check box. This check box is not set by default.

Active graphics - To use a more elaborate and lively set of banners, buttons, bullets, and other graphical elements, the Active Graphics check box is selected by default; to use the normal graphic set, clear the check box. Most Themes include hover buttons; if you plan to use them, make sure that this item is checked.

Background picture - The Background picture check box is selected by default. If you don't want to use it for your Theme, clear the check box.

Tip: The Create new theme... link allows you to customize the Theme. See the article entitled Customizing Themes for Windows SharePoint Services for more information.

5. You can choose to Apply as default theme or Apply to selected page(s). When you select Apply as default theme, new pages that are created automatically use this theme. After you make your selection, the new theme is applied to the page or site.

Tip: It may take a few seconds before the changes are reflected, but behind the scenes a lot is happening. Buttons, bullets, backgrounds, fonts, formatting, and more are being changed throughout the page or the site.

The site look and formatting is now greatly changed in just a few clicks:


Default Site Created with Windows SharePoint Services


Default Site Created with Windows SharePoint Services with Spring Theme Applied
See it in action

The finance, human resources, and sales & marketing sample sites were created with custom Themes. The rules for fonts, backgrounds, buttons, and other elements are specified in the custom Themes.

Adding "OpenInNewWindow" option to SharePoint Links lists

Tangent: List Templates and Site Definitions

For a super fast overview, when a new SharePoint site is created, one of the first steps you take is to select a template to build out the site. These templates are defined in the file system: C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\1033. After selecting a template, SharePoint uses the ONET.XML & SCHEMA.XML file to build out the default lists and adds the default Web Parts to the homepage. The ONET.XML file also contains information about what types of lists can be created once the site has been created. It is within these site definitions and templates where you can create your own OOTB lists for sites and really make some powerful solutions.
For more information on creating your own site defintions, refer to the footnotes.^[2]

Overview

So how are we going to implement this “OpenInNewWindow” feature? We’re going to do it the Microsoft recommended way:

• Part 1: Copy an existing site defintion
• Part 2: Modify the SCHEMA.XML file in our new site definition using CAML

Let’s get started! All my site definitions that I modify from the originals have “my” in the prefix which is the convention I’ll use in this article.

Part 1: Copy an Existing Site Defintion

This section is a very fast tutorial on how to create a new site defintiion from an existing site definition. For more information and a much more detailed walkthrough step-by-step with screenshots along the way, check out Heather’s Add a Custom List to SharePoint - a foray into CAML article.^[2]

Let’s take the most straightforward and common site defintion: Team Site. Create a copy of the the Team Site site definition (C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\1033\STS) and name the new folder MYSTS.
Give New Site Definition A Unique Name
Now, we need to alter the ONET.XML file for our new MYSTS site defintion so that it has a unique name in the Template Picking screen… how else do you plan to distinguish it from the existing Team Site? Open the ONET.XML file for MYSTS (C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\1033\MYSTS\XML\ONET.XML), find the element (should be line #4), and change it’s Title attribute from “Team Web Site” to “myTeam Web Site”, as shown below:

ONET.XML available for download ^[a]
Register the New Site Definition
Now we need to tell SharePoint there’s a new site definition available to users when they create a site. This info is found in WEBTEMP*.XML files, located here: C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\1033\XML. SharePoint looks at all the WEBTEMP*.XML files in the afore mentioned directory for the list of available site definitions. To tell SharePoint about our new site definition, let’s copy the one used for the “Team Web Site” (STS) site definition and modify it for our purposes. Create a copy WEBTEMP.XML and name it WEBTEMPMYSTS.XML.
Open our new WEBTEMPMYSTS.XML. You’ll see two elements as well as a handful of elements. Since we’re only going to use this new file to define only our new site definition, we can get rid of a lot the XML in this file to define one template with one configuration as follows (again, for more information on the structure of this file, refer to Heather’s article as mentioned above):

WEBTEMPMYSTS.XML available for download ^[b]
That’s it, we now have our new site definition created and told SharePoint to offer it in the available site definitions to pick from when creating new WSS sites. For this to take effect, run IISRESET.EXE from a command line and provision/extend a new WSS site (that’s the fun part… you have to reset IIS every time you make changes to a site definition or the WEBTEMP*.XML files). When you reach the Template Selection page, you should see our site definition listed in the available options as the following image does (notice the selected template):

Part 2: Modify the SCHEMA.XML File in Our New Site Defintion Using CAML

At this point we have our own site definition which we can customize to our heart’s content. We’re just interested in a specific list template our new site definition: the one containing the Links list. The Links list template is found in the following folder: C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\1033\MYSTS\LISTS\FAVORITE.

Refer to Heather’s “SharePoint Site Definitions - Maping files to pages on a SharePoint site” ^[2] article for a list of which folder corresponds with each list template.

The FAVORITE folder contains 5 files. The ASPX files are all used for the various pages used in this template. We’ll ignore these for now as they are outside the scope of this article. What we’re really interested in is the SCHEMA.XML file. This is where the real work begins.

For an in-depth explination of the contents of the SCHEMA.XML file, refer to the MSDN article “Customizing Templates for Microsoft Windows SharePoint Services”^[2] and Heather’s article “Add a Custom List to SharePoint - a foray into CAML”.^[2]

Add New Field “Open In New Window”
The first thing we need is a new boolean field that we’ll use to hole the flag if the link should be opened in a new window. We do this by adding a new element in the section of the SCHEMA.XML file. Look for the line that defines the URL field (on or about line #11) that looks like this (take note the type is URL… we’ll revisit this in a second):

Let’s add a new field just after this line:

The attributes say that this field is of type boolean (the user will be presented with a checkbox), the unique ID of the Field (Name), the friendly display name, and if the field is required on this list. If a field is required, the field can’t be removed from the list.
View the New Item Form With The New Field
Save your changes, reset IIS, and open the WSS site you created using our site definition. Go into the Links list and click New Item. The form should look like this:

Go ahead and add two new records, one opening in a new window, one opening in the same window.
Add New Field to Existing Views (optional)
Now we need to add this field to existing views. Personally I wouldn’t add this field to any of the views, but if you wanted to, it’s very simple. Find the “All Links” view by searching for the opening element that defines that view. For example, search for “All Links”, this should take you down to line #156:

Within this view, there’s a element called (around line #702). It currently contains three fields. To add your new field, you’d just add a new tag and assign the Name attribute the name of your new field. Again, I’m not going to do this here.

Anytime you make chages to this file you’ll need to reset IIS to see your changes take effect.

The Problem with the URL Field Rendering
As you saw above, the URL field is of type URL. When a field of type URL is displayd, SharePoint checks to see if a description was entered for the link. If it was, it renders the URL field as description… otherwise it renders it as URL. While this is all fine and good, this poses a problem for our new field. We won’t be able to use the URL property because to open in a new window, we’d need to add in a target=”_blank” to open the link in a new window. Because the whole anchor tag is rendered by the URL type, we’ll need to roll our own implementatin via a computed field (this is how those fields that provide the roll-over drop-down edit menus in certain lists).
Add A New Computed Field
To add a new field, jump back to the top of the file, where we added the OpenInNewWindow field. Add a new element after the existing “Note” field (the Note field should be on or about line #13):

Attributes to take note of:

Attribute:	Description:
Type	Computed implies that this field is calculated from existing fields.
ReadOnly	This marks the field as not editable by a contributor.
AuthoringInfo	Friendly name when a list of fields is displayed (like in the order of the fields presented when editing a view).

Next you need to specify what fields you’re going to use within this computed value. To do this add a element with the necessary elements for each field inside the :

Adding the Rendering Instructions
Now for the big piece: the rendering instructions. Add a element just after the element. I’ll step through this in chuncks as it’s complicated for those not familiar with CAML. What you’re doing is using CAML tags to specify the resulting output.
The first part of the output will be . This is accoplished by this code:




Next we need to determine if the link should be opened in a new window or not. If it is, we need to add target=”_blank” to the anchor tag. Here’s how you do a conditional with CAML (should be fairly straightforward):






Now, close the opening anchor tag:
]]>
To add the text for the link, we need to check one of two properties: and . The WSS SDK explains the two better than I could:

» The Column element is used to return the raw data value for a particular field (as opposed to the formatted version provided by the Field element).
» The Column2 element is used in rendering a hyperlink. In Microsoft Windows SharePoint Services, hyperlinks are stored as two separate values. The actual URL value is stored in one part, and the descriptive text is stored in another. In a Link field, returns the value of the URL, and returns the descriptive text of the hyperlink.
Microsoft WSS SDK^[3]

So… we need to check and see if the element has anything in it. If so, we want to use that to show the link to the user. Otherwise, we’ll just use the URL itself:





All that’s left is t he closing anchor tag:
]]>
That completes our computed field… it should now look like this:

Modified SCHEMA.XML available for download ^[c]
This computed field can now be used in existing or new views as you can see it’s now one of those special options in the field choser within a view settings page (it’s the last one listed in the view below: All Links):

Modify Existing Views to Use The New Computed Column
Now that we have this computed column, we need to make sure the existing views use it when displaying the links. Right now we’re concerned about two different views: the All Links view and the Summary view when the Web Part is placed in a Web Part Zone on a Web Part Page. Let’s first concentrate on the Summary view as the All Links view is a different animal. Look for the Summary view by seaching for this element (should be on or about line #86):

At the end of the element, you’ll see a element (on or about line #177). You will also notice that it contains a single element referring to the URL. Change this to our new computed field: URLNewWinLink. It should look like this:

Modified SCHEMA.XML available for download ^[c]
Now, save your changes, reset IIS, and refresh the homepage of the WSS site you created. Click on the link list item you added that should open in a new window and watch it work! Do the same for the one that should load in the same window. Cool huh?
One Last Finishing Touch
There’s one last finishing touch that I think should be implemented. The All Links summary view displays a special computed column that displays the drop-down edit menu when the mouse hovers over it. Right now, all links open in the same window. This computed field should be modified to open in a new window if so specified. Fortunately, we’ve already done the hard part!
Jump back to the top of the SCHEMA.XML file and find the URLwMenu element (on or about line #40). Add the OpenInNewWindow element to the element just like we did for the URLNewWinLink computed field. If you don’t do this, we won’t be able to access it within the element. Scroll down to the element where it’s starting to build the anchor tag for the link (on or about line #70). The code currently looks like this:

Original URLwMenu computed field; Modified SCHEMA.XML available for download ^[c]
We need to modify it to look like the following (the highlighted portion shows the new code… take note some code was removed as it was prematurely closing the opening anchor tag:

Modified URLwMenu computed field; Modified SCHEMA.XML available for download ^[c]
Save, reset IIS, and refresh your WSS site. Everything works!

InfoPath 2007: Creating a Template Part

Creating a basic Template Part in Microsoft Office InfoPath 2007 is a simple process. However the rewards that come along afterwards when you have a nice library of template parts is quite nice. In this post I will give a high level walkthrough of the steps it takes so you can see yourself how easy they are to create and hopefully recognize a few of the benefits of possibly a little work upfront.
Creating a Template Part in InfoPath 2007
Open InfoPath 2007 and select to Design a Form Template

You are given a choice to create either a complete form or a template part. Because the component you are going to create will be used in multiple forms, it makes sense to package it as a template part instead. In this example, I will create a template part for contact information since it is contained in probably half the forms I make. Even if some slight items change, using a template part will give me a good starting point.
By selecting template part, you are given a choice to create from a blank template or based on an XML document or schema. In this case we will select Blank.

You design your form by adding the appropriate layout tables and controls to the form. It is always a good idea to begin this step with a sketched out idea of what your form will look like on paper and the data the form will collect including any dependencies or connections identified.
Similar to a complete template, you can import data from other data sources such as SQL, web services or SharePoint. In this case, I have a list of provinces contained on a centrally available SharePoint site so I will utilize that. You never know when Canada could decide to recruit a new province or territory so its important to make it easy for this listing to stay up to date. OK So maybe in this case I just hate typing so it’s easier for me to grab this information from a central listing somewhere.

After all my labels and controls have been added, I am ready to save my template part.

When you save the template part you will notice it has its own unique file extension (xtp) rather than the xsn you would see if you were saving a complete form.

Now whenever I want to create a form that contains contact information, I can simply add my template part instead of recreating every single field manually. Who has time for manual recreation of common elements when there are Stanley Cup Finals or World Cup Soccer games to watch?
Below the controls listing on the task pane select the link to “Add or Remove Custom Controls…”

Select Template Part from the wizard screen…

Browse to the location of your template part. If you are working on a team, then it would be a good idea to store these in a central location so as to be a library for everyone to use.

And Voila you have a new custom control available to you in the task pane.


Just like any other control, click and drag it onto the form to make it appear.

Depending on the complexity of your template part, you can evaluate the benefit of using template parts by comparing the length of time it takes to click and drag versus the length of time it took you to add all the controls and set up your data connection, then multiply it by the number of times you would typically have to add those fields to a form.

Add Advanced Search to a Top Level Team Site in MOSS 2007

If you are running Microsoft Office SharePoint Server 2007 (MOSS 2007) and have created a site from a collaborative template such as the Team Site template or Blank Site template, you may notice that by default you do not see the Advanced Search option to the right of your search box as you do when you create a Publishing Portal or Collaboration Portal. The screen shots below illustrate the difference.
Top Level Collaboration Portal Search Box


Top Level Team Site Search Box


A reader of our book asked a great question in our forums on how to add the link if you have a team site as the top level site in your site collection. I supplied a quick answer in forum but then realized it might be a good topic to post about in more detail here.
Basically to get started, in order to use the Advanced Search, you need to have a page from which to perform your query and then another to display the search results. MOSS 2007 has page layouts / template for each of these as well as provides you with customizable web parts if you want to create everything completely from scratch to suit your specific requirements. However the quickest route would be for you to create a sub site on your team site using the Search Center template as this site template already contains the elements you require. This is the same template that is used for the search site in the Collaboration portal which many organizations use as the starting point for their Corporate Intranet. The steps for doing so are described below.

1. From the home page of your top level team site, select Create from the Site Actions menu.
2. Select Sites and Workspaces from the Web Pages category.
3. 
   
   Fill in the details for your new site. Be sure to select the Search Center template under the Enterprise tab. Also it is a good idea to inherit permissions of your top level site since you would likely want to ensure all users of top level site will be able to access the advanced search interface.
   
   
4. Click the Create button to complete the creation of your new search site.
5. 
   
   You will be redirected to the home page of your new search site. The page will be displaying a search box with a link to the Advanced Search page.
   
   
6. Click the Advanced Search link.
7. From the Advanced Search page, copy the url of the page.
8. Select Site Settings from the Site Actions menu.
9. Because you are on a sub site to your top level site where the majority of site collection settings exist, you need to then select Go to Top Level Site Settings.
10. 
    
    Select Search Settings.
    
    
11. 
    
    Select the top option and paste in the url that you copied in step 7. The url should end with /{the url name of your search site}/advanced.aspx.
    
    
12. Click OK.
13. When you return to the home page of your team site, you will now see the Advanced Search link and clicking it will bring you to the Advanced Search page.